| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| /// <summary> | ||
| /// Deals with DataRow objects | ||
| /// </summary> | ||
| internal class DataRowAdapter : PropertyOnlyAdapter |
There was a problem hiding this comment.
Why don't we follow the one class per file practice?
Sorry, something went wrong.
There was a problem hiding this comment.
Core adapters have always been in the same file. Some of them were moved to ExtraAdapter.cs previously due to missing the corresponding type in CoreCLR. Now we are gradually moving them back.
Sorry, something went wrong.
There was a problem hiding this comment.
The question is more about the project in general.
Sorry, something went wrong.
|
Any idea when can I test this change? Looking forward to give it a shot. Thanks, |
Sorry, something went wrong.
|
Maximo Trinidad (@MaximoTrinidad) The release of beta.5 will on 8/3. But you can build powershell locally to verify the fix. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fix #4232
Enable the DataRow/DataRowView adapters in PowerShell Core by moving the implementation from ExtraAdapter.cs to CoreAdapter.cs.
Add basic tests too.