mhozaifaa / meteors.operationresult

Operation result powerful to handle multi statuses, Easy to user with fancy pattern, Support json convention, Wise level state with multi operation , able include collect and into (forkJoin) functionality

Hi there 👋

Currently, I'm busy building cores and architecture softwares 💻

---

meteors.operationresult's Issues

HttpResponseMessage to OperationResult (support full options).

Feature v6.2.1

• think if we replace OperationResultbase to -> OperationResult without Base! as abstract (this feature allow to save same concept and add more extensions later)

• move WithStatusCode extension to Base,

• Append with OperationResult<>,

• Add ctr/method to revice all props as 'Create Instance' (more useing when you have un-know operation-prop take value after plh of condig ).
  ex:

    Status status;
    string message = String.Empty();
    :
    Int statuscode...
    :
    
    if(--cond--){ ..//change status } 
    else if( .... cond ---.... }....
    :
  
    _Operation.Set(status,message,statuscode....); //auto know exactly operationResult

• back to implicity (success) 😉 but for limited types (IList<>,ICollection<>,IEnumerable<>,INumber(int,double,...) .Net7.0) not supported (Tuple,Object, dynamic, any not basic) under see (string)

  OperationResult<List<Foo>> Get() 
  {  return new ();   };

• Stop return null/by default value as Json like as ("", [], {}) SerializerSettings

• Global static Isbody, Global static checkin object to serialize , sme to add xtensions for oepration.

• #7

To add

• interceptor to Set,
• Set method with not base
• enable convert un body operation to any other type data
• global body
• OperationResult without Generic <>

not shown message with Success Status (ToJsonResult)

check : https://github.com/MhozaifaA/Meteors.OperationResult/blob/master/src/ExtensionMethods/OpertaionResultExtesnsion.cs#L101
build and retest unittest as this case

*in Next Release