[Feature]: Implement full semantics for Xcode 27.2 and later projects

Abierto
#22 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
swift
Área
build-system

Línea de trabajo

Start by reading the project’s semantic validation entry points and tests; the issue does not name specific files. Identify how the format represents build phases and Xcode compatibility versions, then determine which Xcode 27.2 semantics are currently unenforced. Done means generated projects are checked against the applicable semantics for their compatibility version.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Describe the feature

Right now it looks like the Xcode-project-format project doesn't really implement many of the semantics of Xcode projects, only the bare minimum required. That is, it doesn't appear to do things like limit the number of Copy Resources build phases per target to one, which would allow one to use the framework to construct invalid projects.

Since Xcode 27.2 is the first release to incorporate this format, it should be a reasonable baseline for the semantics to enforce; any future semantics would of course need to be incorporated in a way that allows variance with the Xcode compatibility version.

Use case

I'd like a reasonable guarantee that a generated project is semantically valid for a particular Xcode version (27.2 or later), rather than just syntactically valid.

Alternatives considered

No response

Additional context

No response

Lenguaje dominante
Swift
Estrellas
544
Forks
36
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apple/xcode-project-format

Todos los issues de apple/xcode-project-format

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.