Skip to content

Improve sproc and function experience #2947

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ErikEJ opened this issue May 2, 2025 · 4 comments
Open

Improve sproc and function experience #2947

ErikEJ opened this issue May 2, 2025 · 4 comments
Labels

Comments

@ErikEJ
Copy link
Owner

ErikEJ commented May 2, 2025

Is there anyway that we could see the schema name in the list of stored procedure when typing:

Entities.Procedures........ etc?

This would be a great help

@paulatmonarch FYI

@ErikEJ
Copy link
Owner Author

ErikEJ commented May 5, 2025

Thinking about just prefixing store procedure and function method names with schema (based on new option)

public virtual async Task<List<CustOrderHistResult>> CustOrderHistAsync(string CustomerID, OutputParameter<int> returnValue = null, CancellationToken cancellationToken = default)

public virtual async Task<List<CustOrderHistResult>> Dbo_CustOrderHistAsync(string CustomerID, OutputParameter<int> returnValue = null, CancellationToken cancellationToken = default)

@paulatmonarch
Copy link

That would be perfect

@kerwinc
Copy link

kerwinc commented May 24, 2025

I can't tell if this is currently possible, but it would be great to be able to apply renaming conversions by defining them in the efpt.renaming.json file. Example:

{
"SchemaName": "special",
"TablePatternReplaceWith": "",
"TableRegexPattern": "^tb_",
"StoredProcedurePatternReplaceWith": "ExecuteSpecial",
"StoredProcedureRegexPattern": "^pr_",
"Tables": [
],
"UseSchemaName": false
},

As well as renaming and storing the related stored proc models in a Results directory under the schema folder.

@ErikEJ
Copy link
Owner Author

ErikEJ commented May 24, 2025

@kerwinc Renaming is supported, and feel free to script file movements after code generation

If you like my free tools, I would be very grateful for a rating/review on Visual Studio Marketplace and/or a one-time or monthly sponsorship

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants