Skip to content
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

Add option for filesystem-centric editing via a web application #464

Closed
isc-tleavitt opened this issue Aug 28, 2024 · 1 comment · Fixed by #466
Closed

Add option for filesystem-centric editing via a web application #464

isc-tleavitt opened this issue Aug 28, 2024 · 1 comment · Fixed by #466
Assignees
Labels
customer Based on customer feedback (as opposed to something identified by developers) enhancement New feature or request usability

Comments

@isc-tleavitt
Copy link
Collaborator

isc-tleavitt commented Aug 28, 2024

It would be helpful if git-source-control had the option to create a web application (say, /git/<namespace>) that doesn't serve files over CSP but does allow editing of source code. This would be like itemsetsourcelink in a CCR context, and would be handy for the following cases:

  • Management of files in the git repo on the server via a real IDE (VSCode)
  • Handling conflicts where the effect of the conflict is to prevent import into IRIS

Edits to such files via VSCode should trigger appropriate import behavior, and the web application files themselves should have menu options based on the corresponding InternalName (if there is one). It is important that this import only happens for mapped files - as a particularly common use case, there might be an edit of a system default settings file for LIVE that we wouldn't want to import into dev!

This would be controlled by a namespace-level setting; changing it would create/delete the web application as appropriate. The default should be not to create such a web application.

@isc-tleavitt isc-tleavitt added the enhancement New feature or request label Aug 28, 2024
@isc-tleavitt isc-tleavitt added this to the Q3/Q4 2024 Targets milestone Aug 28, 2024
@isc-tleavitt
Copy link
Collaborator Author

This is especially important for HCC because there is a guaranteed need to edit files that don't map to items in the database - most importantly, system default settings and other environment-variant files that are edited in dev but take no effect until test/prod.

@isc-tleavitt isc-tleavitt added customer Based on customer feedback (as opposed to something identified by developers) usability labels Aug 28, 2024
@isc-tleavitt isc-tleavitt self-assigned this Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer Based on customer feedback (as opposed to something identified by developers) enhancement New feature or request usability
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant