[PRE REVIEW]: Jangular: A Full-Stack Framework for Java and Angular Integration

[editorialbot]

Submitting author: @nathangtg (Nathan Aldyth Prananta Ginting)
Repository: https://github.com/nathangtg/jangular-cli
Branch with paper.md (empty if default branch):
Version: v1.3.0
Editor: Pending
Reviewers: Pending
Managing EiC: Daniel S. Katz

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/1147eb8cc52c85dcd5b63781f14b223d"><img src="https://joss.theoj.org/papers/1147eb8cc52c85dcd5b63781f14b223d/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/1147eb8cc52c85dcd5b63781f14b223d/status.svg)](https://joss.theoj.org/papers/1147eb8cc52c85dcd5b63781f14b223d)

Author instructions

Thanks for submitting your paper to JOSS @nathangtg. Currently, there isn't a JOSS editor assigned to your paper.

@nathangtg if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.

Editor instructions

The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:

@editorialbot commands

[editorialbot]

Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

✅ OK DOIs

- None

🟡 SKIP DOIs

- No DOI given, and none found for title: JHipster - Full Stack Platform for the Modern Deve...
- No DOI given, and none found for title: Creating an application
- No DOI given, and none found for title: Monitoring your JHipster Applications
- No DOI given, and none found for title: Setting up Continuous Integration
- No DOI given, and none found for title: Nx and the Angular CLI
- No DOI given, and none found for title: Nx Enterprise POV
- No DOI given, and none found for title: Scaffold Angular applications with rspack
- No DOI given, and none found for title: Enterprise-Grade Security, Built Into the Core
- No DOI given, and none found for title: The Fullstack React Framework
- No DOI given, and none found for title: Authentication
- No DOI given, and none found for title: NestJS - A progressive Node.js framework
- No DOI given, and none found for title: An Overview Of Typescript, Angular And Nest JS
- No DOI given, and none found for title: Nest.js, or Angular and Spring on the backend
- No DOI given, and none found for title: Artisan Console
- No DOI given, and none found for title: Blade Templates
- No DOI given, and none found for title: Laravel commands: Top Artisan commands to know and...
- No DOI given, and none found for title: How to Create Custom Laravel Commands with PHP Art...
- No DOI given, and none found for title: Taylor Otwell on the Importance of Documentation a...
- No DOI given, and none found for title: A Guide to Running a Full-Stack Angular Applicatio...
- No DOI given, and none found for title: Common Spring Boot & Angular Integration Pitfalls
- No DOI given, and none found for title: spring-angular-monorepo
- No DOI given, and none found for title: 5 reasons you should be doing container native dev...
- No DOI given, and none found for title: What is "Kubernetes Native" CI/CD: History, Key To...
- No DOI given, and none found for title: What Is Developer Experience & 17 Ways To 10x Your...
- No DOI given, and none found for title: Why Developer Experience (DevEx) is Business Criti...
- No DOI given, and none found for title: Developer Experience (DevEx) Trends Shaping 2024
- No DOI given, and none found for title: New Atlassian research on developer experience hig...
- No DOI given, and none found for title: Developer experience
- No DOI given, and none found for title: Internal Developer Portals: what you need to know
- No DOI given, and none found for title: How GitHub Approaches Internal Developer Experienc...

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.98  T=0.57 s (2621.8 files/s, 193139.8 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
JavaScript                     827           2676           3929          41478
JSON                            64              0              0          15064
TypeScript                     555           2145          22048          12181
Markdown                        43           2984              2           7414
Text                             6             48              0            238
TeX                              1             29              0            210
YAML                             2              8              6            114
Dockerfile                       2             20             22             31
HTML                             2              0              0              2
-------------------------------------------------------------------------------
SUM:                          1502           7910          26007          76732
-------------------------------------------------------------------------------

Commit count by author:

    58	nathangtg
     1	Nathan G

[editorialbot]

Paper file info:

📄 Wordcount for paper.md is 1084

✅ The paper includes a Statement of need section

[editorialbot]

License info:

✅ License found: MIT License (Valid open source OSI approved license)

[editorialbot]

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

[editorialbot]

Five most similar historical JOSS papers:

FAME-Core: An open Framework for distributed Agent-based Modelling of Energy systems
Submitting author: @KriNiTi
Handling editor: @fraukewiese (Active)
Reviewers: @xtruan, @pgranato
Similarity score: 0.5942

uJVM: Lightweight Java Virtual Machine for embedded systems
Submitting author: @omoliavko
Handling editor: @gkthiruvathukal (Active)
Reviewers: @morganericsson, @hainesr
Similarity score: 0.5885

BiGGer: A Model Transformation Tool written in Java for Bigraph Rewriting in GrGen.NET
Submitting author: @PioBeat
Handling editor: @vissarion (Active)
Reviewers: @abhishektiwari, @idoby
Similarity score: 0.5863

omni-fig: Unleashing Project Configuration and Organization in Python
Submitting author: @felixludos
Handling editor: @gkthiruvathukal (Active)
Reviewers: @julianpistorius, @jarrah42
Similarity score: 0.5850

Mantik: A Workflow Platform for the Development of Artificial Intelligence on High-Performance Computing Infrastructures
Submitting author: @rico-berner
Handling editor: @arfon (Active)
Reviewers: @zhaozhang, @gflofst
Similarity score: 0.5846

⚠️ Note to editors: If these papers look like they might be a good match, click through to the review issue for that paper and invite one or more of the authors before considering asking the reviewers of these papers to review again for JOSS.

[danielskatz]

👋 @nathangtg - thanks for your submission.

I have some questions before we proceed:

1. What is the relationship of this work and https://www.npmjs.com/package/jangular?
2. Is all the source code in this repo your work, or is any forked or copied from elsewhere? I want to be sure I understand what your contribution is that we would be reviewing.

In addition, your paper has some issues: it has no references section, and no references, though you have a bib file with a lot of entries. Please follow the example paper, noting the References heading at the end, and the fact that anything that you want to references must have a citation in the paper body. If you have entries in the bib file that aren't actually cited in the paper body, you can remove them. Please make changes, then use the command @editorialbot generate pdf to make a new PDF. editorialbot commands need to be the first entry in a new comment.

[nathangtg]

Hello @danielskatz ,

Thank you very much for your thoughtful review and helpful questions. I truly appreciate the opportunity to clarify a few points and improve my submission:

1. Relationship to Jangular:
   There is no affiliation between my project and the Jangular package on npm. The name Jangular CLI was chosen simply because it felt fitting for a CLI tool designed to support Angular and Java development. My project is entirely independent and unrelated to the existing npm package.

2. Source Code Ownership:
   All the code in this repository is written entirely by me. The project has not been forked from any other sources and does not include copied code. It was built from scratch as part of my personal learning and development.

3. References and Citations:
   I sincerely appreciate the reminder regarding citations. Initially, I had removed them under the mistaken impression that they might not be required, which was an oversight on my part. As this is my first time preparing a submission like this independently, I now realize how important it is to follow the example paper closely. I’ve since revised the main paper to properly include in-text citations and will ensure the references section is complete and clean, with any unused entries removed from the .bib file. I will also regenerate the PDF as requested.

Thank you again for your time and guidance. I’m grateful for the feedback and will make the necessary updates as soon as possible.

[nathangtg]

@editorialbot generate pdf

[editorialbot]

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

[editorialbot]

Five most similar historical JOSS papers:

FAME-Core: An open Framework for distributed Agent-based Modelling of Energy systems
Submitting author: @KriNiTi
Handling editor: @fraukewiese (Active)
Reviewers: @xtruan, @pgranato
Similarity score: 0.5591

Mantik: A Workflow Platform for the Development of Artificial Intelligence on High-Performance Computing Infrastructures
Submitting author: @rico-berner
Handling editor: @arfon (Active)
Reviewers: @zhaozhang, @gflofst
Similarity score: 0.5561

ur-scape: harnessing data for stakeholder participation in city-making processes
Submitting author: @luyuhao0326
Handling editor: @hugoledoux (Active)
Reviewers: @winstonyym, @cforgaci
Similarity score: 0.5505

tfaip - a Generic and Powerful Research Framework for Deep Learning based on Tensorflow
Submitting author: @chwick
Handling editor: @arfon (Active)
Reviewers: @levimcclenny, @Het-Shah
Similarity score: 0.5489

Viash: A meta-framework for building reusable workflow modules
Submitting author: @rcannood
Handling editor: @danielskatz (Active)
Reviewers: @wilkinson, @abhishektiwari, @mberacochea
Similarity score: 0.5489

⚠️ Note to editors: If these papers look like they might be a good match, click through to the review issue for that paper and invite one or more of the authors before considering asking the reviewers of these papers to review again for JOSS.

[danielskatz]

@nathangtg - thanks for the changes.

I have one remaining question:

Can you explain how this is research software as defined by JOSS?

I'm going to ask the editors to discuss this, in part based on the your response here, but also based on the paper and the software. You should hear back in a week or two.

[danielskatz]

@editorialbot query scope

[editorialbot]

Submission flagged for editorial review.

[nathangtg]

Thank you for your question @danielskatz about how Jangular CLI fits JOSS's definition of research software. I acknowledge that my tool was not primarily designed as research software and is targeted more broadly at developers, including indie developers and those working on rapid prototyping. However, after reviewing the guidelines, I believe it may still qualify and benefit the research community in the following ways:

Research Software Justification:

Jangular CLI addresses architectural and systems engineering challenges in research software development contexts, particularly:

1. Supporting research experiments: Many computational research projects require web-based interfaces for data collection, visualization, and experiment deployment. Jangular CLI significantly reduces the technical barriers to creating robust Angular/Java applications for experimental platforms, allowing researchers to focus on their core scientific questions rather than technical implementation details.

2. Solving complex modeling problems: The tool implements architectural design patterns that solve the complex modeling challenge of maintaining consistency between frontend and backend data models in research applications - a critical issue in systems that handle research data.

3. Enabling new research approaches: By automating the tedious aspects of full-stack development, the tool enables researchers without extensive programming backgrounds to more easily create software artifacts for their studies, particularly in human-computer interaction, digital humanities, and citizen science projects.

The scholarly effort represented includes not just the code itself, but the research into effective architectural patterns for cross-layer consistency, the development of templates that enforce research software best practices, and documentation that makes these approaches accessible to the research community.

While I recognize Jangular CLI operates at a meta-level by helping create research software rather than being research software itself, I believe tools that significantly advance how researchers build software systems fall within JOSS's mission to improve the quality and sustainability of research software.

I understand that the primary audience for my tool includes indie developers and those focused on rapid prototyping, but I believe the acceleration of development workflows it provides would be particularly valuable to researchers who need to quickly implement software systems but may not have extensive development resources or time.

I appreciate your consideration and am open to any feedback if you feel this still falls outside JOSS's scope. If it does not meet JOSS requirements, I completely understand and would welcome suggestions for more appropriate venues.

[danielskatz]

👋 @nathangtg - I'm sorry to say that after discussion amongst the JOSS editors, we have decided that this submission is not research software as defined by JOSS. This does not mean that it is not software that is useful in research, but just that JOSS does not consider it in scope for review as research software. Please see https://joss.readthedocs.io/en/latest/submitting.html#other-venues-for-reviewing-and-publishing-software-packages for other suggestions for how you might receive credit for your work.

[danielskatz]

@editorialbot reject

[editorialbot]

Paper rejected.